SUPPORT

Select Your Region

Visit the Cary, NC, US corporate headquarters site

Americas

Europe

Middle East & Africa

Asia Pacific

View our worldwide contacts list for help finding your region

Americas

Europe

Middle East & Africa

Asia Pacific

Sign In

Get access to My SAS, trials, communities and more.

Sign Out

Get access to My SAS, trials, communities and more.

SAS Sites

sas.com
Support
Blogs
Communities
Developer
Curiosity
Videos

Documentation

Learn
Brand
PartnerNet
Merchandise
SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 58121: Intermittent failures occur when you attempt to log on to SAS® Visual Analytics or other SAS® client applications

DetailsHotfixAboutRate It

An intermittent failure might occur when you attempt to log on to SAS Visual Analytics or another SAS client application.

The error message reported to the SAS-configuration-directory/Web/WebAppServer/SASServer##/logs/server.log file might look similar to the following:

2016-04-27 14:03:12,350 ERROR (tomcat-http--50) [org.apache.catalina.core.ContainerBase.[Catalina].[localhost]. [/SASVisualAnalyticsViewer].[jsp]] Servlet.service() for servlet [jsp] in context with path [/SASVisualAnalyticsViewer] threw exception java.lang.IllegalStateException: Unable to find local session... at com.sas.svcs.authentication.helper.UserSessionFactory.getLocalSession(UserSessionFactory.java:187) ... Caused by: com.sas.services.security.CredentialLoginServiceException: The application could not log on to the server "mymetahost.mycompany.com:8561". The user ID "myuser" or the password is incorrect. [ com.sas.services.security.login.CredentialException: The application could not log on to the server "mymetahost.mycompany.com:8561". The user ID "myuser" or the password is incorrect. [ com.sas.services.connection.InvalidCredentialsException: The application could not log on to the server "mymetahost.mycompany.com:8561". The user ID "myuser" or the password is incorrect. [ org.omg.CORBA.NO_PERMISSION: Access denied. [ com.sas.iom.SASIOMDefs.GenericError: Unable to contact the LDAP server. [ com.sas.iom.SASIOMDefs.GenericError: Possible cause: Server certificate not found, port not SSL enabled [ com.sas.iom.SASIOMDefs.GenericError: LDAP SSL Message ldapsNegotiate() failed -2143305722. [ com.sas.iom.SASIOMDefs.GenericError: Possible cause: Server certificate not found, port not SSL enabled [ com.sas.iom.SASIOMDefs.GenericError: LDAP SSL Message ldapsNegotiate() failed -2143305722. [ com.sas.iom.SASIOMDefs.GenericError: Possible cause: Server certificate not found, port not SSL enabled [ com.sas.iom.SASIOMDefs.GenericError: LDAP SSL Message ldapsNegotiate() failed -2143305722. [ com.sas.iom.SASIOMDefs.GenericError: Possible cause: Server certificate not found, port not SSL enabled [ com.sas.iom.SASIOMDefs.GenericError: LDAP SSL Message ldapsNegotiate() failed -2143305722. ] ] ] ] ] ] ] ] ] ] ] ] at com.sas.services.user.UserContext.authenticate(UserContext.java:2471) ... Caused by: com.sas.iom.SASIOMDefs.GenericError: Unable to contact the LDAP server. at com.sas.iom.orb.brg.Engine.parseErrorXML(Engine.java:2049) ... 103 more Caused by: com.sas.iom.SASIOMDefs.GenericError: Possible cause: Server certificate not found, port not SSL enabled ... 104 more Caused by: com.sas.iom.SASIOMDefs.GenericError: LDAP SSL Message ldapsNegotiate() failed -2143305722.

The error occurs when SSL has been configured for the connection to the LDAP/Active Directory server.

The error stack traces show that the return code of -2143305722 is logged many times. This error code indicates that a time-out has occurred during the negotiation of the SSL connection to the LDAP/Active Directory server.

Without debug logging enabled, the metadata server log located in the SAS-configuration-directory/SASMeta/MetadataServer/Logs directory might report the following message:

2016-03-05T12:28:41,084 WARN [84315] :sas - New client connection (2147) rejected from server port 8561 for user myuser. Peer IP address and port are [::ffff:10.182.29.54]:54236 for APPNAME=Visual Analytics Transport Service 7.1.

In order to verify that you are encountering the problem, you need to enable debug logging as discussed in SAS Note 51911: "Troubleshooting SAS® Metadata Server authentication issues in SAS® 9.3 and later."

The debug logging shows that the following messages occur in the log just prior to the "New client connection (####) rejected" message:

2016-03-05T12:28:41,083 DEBUG [84315] :sas - called tkWait, status: -2143305722 2016-03-05T12:28:41,084 DEBUG [84315] :sas - Leaving ldapNegotiate, status: -2143305722 2016-03-05T12:28:41,084 DEBUG [84315] :sas - ldapsNegotiate failed 2016-03-05T12:28:41,084 TRACE [84315] :sas - ldap_open: failed 2016-03-05T12:28:41,084 DEBUG [84315] :sas - tkldOpen encountered a failure in ldap_open. 2016-03-05T12:28:41,084 DEBUG [84315] :sas - Provider failed: 80bfd100

To work around the problem, disable SSL when connecting to the LDAP/Active Directory server.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Metadata ServerMicrosoft® Windows® for x649.49.4_M49.4 TS1M4
Microsoft Windows 8 Enterprise 32-bit9.49.4_M49.4 TS1M4
Microsoft Windows 8 Enterprise x649.49.4_M49.4 TS1M4
Microsoft Windows 8 Pro 32-bit9.49.4_M49.4 TS1M4
Microsoft Windows 8 Pro x649.49.4_M49.4 TS1M4
Microsoft Windows 8.1 Enterprise 32-bit9.49.4_M49.4 TS1M4
Microsoft Windows 8.1 Enterprise x649.49.4_M49.4 TS1M4
Microsoft Windows 8.1 Pro 32-bit9.49.4_M49.4 TS1M4
Microsoft Windows 8.1 Pro x649.49.4_M49.4 TS1M4
Microsoft Windows 109.49.4_M49.4 TS1M4
Microsoft Windows Server 20089.49.4_M49.4 TS1M4
Microsoft Windows Server 2008 R29.49.4_M49.4 TS1M4
Microsoft Windows Server 2008 for x649.49.4_M49.4 TS1M4
Microsoft Windows Server 2012 Datacenter9.49.4_M49.4 TS1M4
Microsoft Windows Server 2012 R2 Datacenter9.49.4_M49.4 TS1M4
Microsoft Windows Server 2012 R2 Std9.49.4_M49.4 TS1M4
Microsoft Windows Server 2012 Std9.49.4_M49.4 TS1M4
Windows 7 Enterprise 32 bit9.49.4_M49.4 TS1M4
Windows 7 Enterprise x649.49.4_M49.4 TS1M4
Windows 7 Home Premium 32 bit9.49.4_M49.4 TS1M4
Windows 7 Home Premium x649.49.4_M49.4 TS1M4
Windows 7 Professional 32 bit9.49.4_M49.4 TS1M4
Windows 7 Professional x649.49.4_M49.4 TS1M4
Windows 7 Ultimate 32 bit9.49.4_M49.4 TS1M4
Windows 7 Ultimate x649.49.4_M49.4 TS1M4
64-bit Enabled AIX9.49.4_M49.4 TS1M4
64-bit Enabled Solaris9.49.4_M49.4 TS1M4
HP-UX IPF9.49.4_M49.4 TS1M4
Linux for x649.49.4_M49.4 TS1M4
Solaris for x649.49.4_M49.4 TS1M4
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.